Skip to content

backport(v0.5.x): present the launch ticket to the KMS - #1579

Open
kvinwang wants to merge 1 commit into
release/v0.5.xfrom
backport/v0.5.x-launch-ticket
Open

kvinwang wants to merge 1 commit into
release/v0.5.xfrom
backport/v0.5.x-launch-ticket

Conversation

@kvinwang

Copy link
Copy Markdown
Collaborator

Backports the guest side of #1577 to 0.5.x, so a 0.5.x guest can boot an app whose contract requires a launch ticket. Without it, the guest never sends the ticket a 0.6.4 VMM writes to its sys-config, and a 0.6.4 KMS refuses it as Invalid launch ticket.

  • SysConfig gains launch_ticket. It is never put in vm_config, which attestations embed.
  • GetAppKeyRequest and SignCertRequest gain launch_ticket = 5, matching feat: KMS-enforced launch tickets #1577. dstack-util sends it in GetAppKey, and CertRequestClient in SignCert, for both dstack-util and the guest agent.

Not included: the KMS, contract, auth backend and VMM parts, and KMS onboarding, which stay on 0.6.4. A 0.5.x KMS ignores the new fields.

Tests: cargo test for dstack-types, cert-client, dstack-util and dstack-guest-agent; cargo check --tests for dstack-kms and dstack-gateway.

Signed-off-by: Kevin Wang <wy721@qq.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant